Skip to content

Improve formulation builder disabled-state accessibility#1226

Closed
BigSimmo wants to merge 4 commits into
mainfrom
cursor/formulation-accessibility-final-14d4
Closed

Improve formulation builder disabled-state accessibility#1226
BigSimmo wants to merge 4 commits into
mainfrom
cursor/formulation-accessibility-final-14d4

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • replace opacity-only disabled styling on formulation builder navigation with explicit token-based disabled surfaces
  • preserve native disabled semantics while keeping labels readable in light, dark, and forced-colors modes
  • add Playwright coverage for disabled state, focus rejection, enabled transitions, and axe
  • update Create label.yml #64 while leaving the unavailable historical worktree untouched

RAG impact: no retrieval behaviour change — UI-only disabled-state styling; no retrieval, ranking, answer, or source behavior changed.

Verification

  • npm run verify:pr-local — passed on this clean current-main branch; includes build, client-bundle secret scan, 3,421 unit tests, and offline RAG fixture validation
  • npm run verify:ui — equivalent product/test content passed all seven formulation journeys in earlier hosted Production UI; this final branch requires its own clean hosted Production UI before merge
  • npm run verify:release — not run; provider-backed and not required for this UI-only change
  • Focused formulation Chromium: 2/2 passed on this exact branch
  • npm run verify:cheap: 3,421/3,421 passed

Risk and rollout

  • Risk: Low — scoped Tailwind utility changes on two natively disabled buttons; no logic, API, data, auth, or clinical-output behavior changes.
  • Rollback: Revert 8cd8cb01; no database or migration rollback is involved.
  • Provider or production effects: None.

Clinical Governance Preflight

N/A — UI-only disabled-state presentation; no ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, production environment, or clinical output behavior changed.

Notes

Open in Web Open in Cursor 

Summary by CodeRabbit

  • Bug Fixes

    • Improved disabled navigation controls in the formulation builder with clearer visual states.
    • Disabled controls no longer fade their text and cannot receive focus when unavailable.
  • Tests

    • Added accessibility and regression coverage for disabled navigation behavior.
    • Expanded browser checks to verify enabled states, focus handling, and WCAG compliance.
  • Documentation

    • Updated review and outstanding-issue records to reflect the finalized formulation fix and readiness for release.

cursoragent and others added 3 commits July 25, 2026 16:37
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@supabase

supabase Bot commented Jul 25, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@BigSimmo BigSimmo added the skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR label Jul 25, 2026 — with Cursor
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The formulation builder now uses explicit disabled navigation styling without reduced text opacity. Browser tests cover disabled focus behavior, enabled transitions, and axe violations. Documentation records the final branch, reviewed scope, superseded PRs, and hosted-check requirements.

Changes

Formulation accessibility and review status

Layer / File(s) Summary
Disabled navigation styling and browser coverage
src/components/formulation/formulation-builder-page.tsx, tests/ui-formulation.spec.ts
Navigation buttons use explicit disabled classes while retaining full text opacity; Playwright tests verify disabled focus behavior, state transitions, and blocking axe violations.
Final branch review records
docs/branch-review-ledger.md, docs/outstanding-issues.md
Ledger entries identify the reviewed branch and commit, closed superseded PRs, preserved worktree status, and required hosted checks.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main UI accessibility change to formulation builder disabled states.
Description check ✅ Passed The description follows the template with Summary, Verification, Risk and rollout, Clinical Governance Preflight, and Notes sections.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/formulation-accessibility-final-14d4

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…cessibility-final-14d4

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
src/components/formulation/formulation-builder-page.tsx (1)

681-681: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider extracting shared disabled-state classes.

Both buttons repeat the same disabled:cursor-not-allowed disabled:border-[color:var(--border)] disabled:bg-[color:var(--surface-inset)] string. A small shared constant (e.g. disabledNavClasses) would prevent future drift between the two buttons' disabled treatment.

Also applies to: 691-691

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/formulation/formulation-builder-page.tsx` at line 681, Extract
the repeated disabled-state utility classes from the two navigation buttons into
a shared constant such as disabledNavClasses, then interpolate or reuse that
constant in both className values so their disabled styling remains
synchronized.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/components/formulation/formulation-builder-page.tsx`:
- Line 681: Extract the repeated disabled-state utility classes from the two
navigation buttons into a shared constant such as disabledNavClasses, then
interpolate or reuse that constant in both className values so their disabled
styling remains synchronized.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3455b4c8-904e-42d1-bbdc-8c233aea60ee

📥 Commits

Reviewing files that changed from the base of the PR and between 0b82a82 and 369ca04.

📒 Files selected for processing (4)
  • docs/branch-review-ledger.md
  • docs/outstanding-issues.md
  • src/components/formulation/formulation-builder-page.tsx
  • tests/ui-formulation.spec.ts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants